Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zenodo #147

Merged
merged 10 commits into from
Oct 9, 2023
Merged

Zenodo #147

merged 10 commits into from
Oct 9, 2023

Conversation

d70-t
Copy link
Contributor

@d70-t d70-t commented Oct 9, 2023

This is a first shot at #145. However, the more involved parts are still missing. We should probably have:

  • creators: The list of authors, including names, affiliations, orcid
  • license: Which license do we have / want? cc-zero ?
  • upload_type: e.g. dataset or software?
  • keywords ...

here are more options

@d70-t d70-t mentioned this pull request Oct 9, 2023
@observingClouds
Copy link
Collaborator

Thanks @d70-t to start working on this. So far I have always changed the metadata on the Zenodo interface after the automatic upload but the deposition file seems to be a more consistent approach.

As the deposition influences the citation format, I think we should first settle on a format that we like. I suggest

EUREC4A community (2023). EUREC4A [Data set]. Zenodo. 10.5281/ZENODO

This would imply the following parameters:
upload_type: dataset (because we like the intake catalog to become the EUREC4A Dataset)
title: EUREC4A (this would result in a reference like ...EUREC4A [Data set]...)
creators: EUREC4A community

@d70-t
Copy link
Contributor Author

d70-t commented Oct 9, 2023

I like using "EUREC4A community" as author, makes things a lot easier.

I'm a bit hesitant to call the thing "EUREC4A" instead something like "EUREC4A Intake catalogue", because it's a bit unspecific. On the other hand, the goal of this repository is to provide "the EUREC4A dataset", so it's probably the right thing to do?

@d70-t
Copy link
Contributor Author

d70-t commented Oct 9, 2023

Do you have any preferences license-wise?
I'd go for cc-zero, because I think it's the most useful one for datasets

It's hard to make reasonable use of datasets without stating where the data is from, so people will do it 👍. On the other hand, formalizing a requirement to name authors potentially prevents good uses, because depending on the use, it can be hard to e.g. display a predefined statement. Also if we use "EUREC4A community" as author, I guess it's even less useful to go with something like cc-by.

@d70-t d70-t marked this pull request as ready for review October 9, 2023 14:24
@d70-t d70-t requested a review from observingClouds October 9, 2023 14:24
@observingClouds
Copy link
Collaborator

I like using "EUREC4A community" as author, makes things a lot easier.

I'm a bit hesitant to call the thing "EUREC4A" instead something like "EUREC4A Intake catalogue", because it's a bit unspecific. On the other hand, the goal of this repository is to provide "the EUREC4A dataset", so it's probably the right thing to do?

Yeah, this is exactly my thought. Currently "EUREC4A dataset" is maybe a bit vague as the catalog's entries are not immutable but that's where we wanna get to.

@observingClouds
Copy link
Collaborator

The license is a bit tricky as we reference other data sets that might have specific license. However, for this specific repository I would argue that cc_zero is fine, but we should add a note somewhere on how people should add credits to the underlying data and adhere to the EUREC4A data policy.

@d70-t
Copy link
Contributor Author

d70-t commented Oct 9, 2023

I just added a note on the data policy and a (very tiny) description of the catalog. Is it still fine?

@observingClouds
Copy link
Collaborator

Yes, awesome!

@d70-t
Copy link
Contributor Author

d70-t commented Oct 9, 2023

Ok, let's see where this will take us...

@d70-t d70-t merged commit 114126d into eurec4a:master Oct 9, 2023
2 checks passed
@d70-t d70-t deleted the zenodo branch October 9, 2023 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants